The workloadVersion field causes native builds (WinUI, etc.) to fail when
the pre-installed SDK version doesn't match the pinned workload version.
Native builds skip the SDK/workload install step but still need dotnet.

Managed builds get workloads via 'dotnet workload restore' which uses
the SDK's bundled manifests — no global.json pin needed.

dotnet workload restore requires a project/solution file but there is
none in the repo root. Revert to explicit dotnet workload install with
the specific workload IDs needed by the repo.

- Add DOTNET_WORKLOAD_VERSION variable (10.0.103) to azure-templates-variables.yml
- Pass to install-dotnet-workloads.ps1 via -WorkloadVersion parameter
- Script uses 'dotnet workload install --version' for reproducible workload sets
- Keep global.json clean (no workloadVersion) so native builds aren't affected
- Update documentation to reflect new approach

- Update DOTNET_WORKLOAD_TIZEN to 10.0.123 (latest available for 10.0.100 band)
- Pass --dotnet-target-version-band 10.0.100 to Samsung's install scripts
  since their LatestVersionMap doesn't have .NET 10 entries yet

.NET 10 Apple workloads use Xcode 26 unified SDK versioning:
- iOS/MacCatalyst/tvOS/macOS TPV: 18.0/15.0 → 26.0

SupportedOSPlatformVersion minimums bumped in .NET 9/10 workloads:
- iOS/tvOS: 10.0 → 12.2
- MacCatalyst: 13.1 → 15.0
- macOS: 10.14 → 12.0

The Samsung Tizen workload must be installed before 'dotnet workload install
--version' locks the SDK into workload-set mode. Reorder to install Tizen
first via Samsung scripts, then official workloads with version pinning.

…or device tests

- Remove --version from dotnet workload install to avoid workload-set mode
  which makes the SDK ignore Samsung Tizen manifests installed separately
- Update WindowsSdkPackageVersion from 10.0.19041.27 to 10.0.19041.38
  (required by WindowsAppSDK 1.7)
- Add explicit TPVs to MauiTargetFrameworksApp* (26.0 for Apple, 36.0 for
  Android) to avoid resolving to default TPV 26.2 which requires Xcode 26.2
- Update build.cake device test TFMs to match TPV-qualified forms
- Remove unused DOTNET_WORKLOAD_VERSION pipeline variable

- Force manifest update mode with 'dotnet workload config --update-mode
  manifests' before installing workloads. .NET 10 SDK auto-switches to
  workload-set mode which ignores Samsung Tizen manifests.
- Use --skip-manifest-update to prevent official workload install from
  downloading a workload set and overriding manifest mode.
- Install Tizen AFTER official workloads (order doesn't matter in manifest mode).
- Use net9.0 TFMs for iOS/MacCatalyst device tests because net10.0 Apple
  SDK packs (both 26.0 and 26.2) require Xcode 26.0+ which CI doesn't have.
- Add Previous TFMs to device test project so net9.0 builds are available.

Debug Tizen install: show manifest directory contents and dotnet
workload list before and after official workload install to understand
why Samsung.Tizen FrameworkReference is not recognized.

- Set buildExternals default to 155857 to skip native rebuilds
- SkiaSharp.Tests: Add TFMPrevious so device tests can reference it
  from net9.0 TFMs (NU1201: not compatible)
- SkiaSharp.Tests.Devices: Bump MacCatalyst min to 15.0 (workload minimum)

Tizen SDK 10.0.123 only defines KnownFrameworkReference for TPV 8.0+.
TPV 7.0 is listed as supported but has no Samsung.Tizen framework ref,
causing NETSDK1073 'Samsung.Tizen was not recognized'.

- Remove --skip-manifest-update from official workload install:
  The flag prevented downloading manifests, so workloads had nothing
  to install (empty 'Successfully installed workload(s) .' output).
- Fix WASM AOT P/Invoke type conflict: Test used int/int signature
  for hb_script_get_horizontal_direction but binding uses uint/Direction.
  .NET 10 WASM AOT compiler flags this as a C-level type conflict.

The HarfBuzzSharp binding declares Direction as int-backed enum with
uint32_t parameter. The test must match: int32_t return, uint32_t param.
Previous fix incorrectly used uint32_t for both.

MAUI 10.0.0 dropped Tizen support entirely - the NuGet package has no
net10.0-tizen* assemblies. Samsung Tizen 10.0.123 workload removed
KnownFrameworkReference for TPV 7.0 (needed by MAUI 9.0), making
net9.0-tizen7.0 MAUI builds impossible too.

Non-MAUI Tizen support (NativeAssets, bindings) still works with
net9.0-tizen8.0 and net10.0-tizen10.0.

- Remove Microsoft.Maui.Controls.Compatibility.Hosting from MAUI sample
  (namespace removed in MAUI 10.0)
- Remove Tizen from MAUI sample TargetFrameworks (MAUI 10 dropped Tizen)
- Update Tizen sample tizen-manifest.xml api-version to 13 (matches
  TPV 10.0 → API level 13 in Samsung SDK 10.0.123)
- Update Apple ref package names in UpdateDocs.cake for TPV 26.0

…e sample TFMs

- Block TypeScript recompilation in Blazor csproj to fix .NET 10 static web
  assets compression race condition (TypeScriptCompileBlocked=true)
- Update VERSIONS.txt: Apple ref pack names from net8.0_17.0 to net10.0_26.0,
  MAUI versions from 8.0.3 to 10.0.31, tvOS ref pack name updated
- Switch Apple sample apps (iOS, MacCatalyst, MAUI, Uno) to net9.0 TFMs since
  net10.0 Apple TFMs require Xcode 26.0+ (CI has Xcode 16.2)

With the .NET 10 SDK, bare net9.0-ios resolves to TPV 26.0 (not 18.0),
which requires Xcode 26.0. Explicit TPVs (net9.0-ios18.0, net9.0-maccatalyst18.0)
are needed to match the Xcode 16.2 available on CI.

iOS SDK 18.0 requires minimum SupportedOSPlatformVersion of 12.2.

The truncation-based comparison with (int)(v * pow) / pow doesn't
handle negative values correctly near precision boundaries.
For example, -4.9999995 truncates to -4.9999 (not -5.0), causing
false test failures.

This became apparent with .NET 9+ which changed Matrix4x4.CreateFromAxisAngle
to go through Quaternion, producing slightly different floating-point results.

Using Math.Round() is the correct approach for floating-point similarity
comparison.

- Add Apple TPV 26.0 unified SDK versioning note
- Add SupportedOSPlatformVersion section
- Add global.json rollForward and workloadVersion warnings
- Add Docker images section
- Add Known Issues section (floating-point precision, Apple TPVs, MAUI breaking changes)
- Add CI Troubleshooting section (artifact reuse, SDK mismatch, workload install)
- Update workload pinning explanation

- nuget.org is disallowed in CI, must be removed before merging
- buildExternals must be reset to 'latest' before merging
- Add note about temporarily adding nuget.org during development

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- Move ANDROID_AVD_HOME/EMULATOR_HOME setup from cake to YAML pipeline
  (fixes XDG path mismatch on Linux CI agents)
- Remove nuget.org from nuget.config (was temporary workaround)
- Remove manifest mode override from workload install script
  (use default workload version sets now that .NET 10 packages are published)
- Simplify config.ini partition size code to use ANDROID_AVD_HOME env var

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Workload-set mode resolves to 10.0.104 which requires packages
(e.g. microsoft.macos.sdk.net9.0_26.2 v26.2.9000) not yet mirrored
to the dnceng feeds. Manifest mode uses the SDK's bundled manifests
which only reference packages available at SDK release time.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Even in manifest mode, dotnet workload install tries to update manifests
which resolves to packages (e.g. microsoft.ios.windows.sdk.net9.0_26.2
v26.2.9000) not available in the dnceng feeds. --skip-manifest-update
forces use of the SDK's bundled manifests only.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The missing packages just need mirroring to dnceng, not a workaround.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Pass --version to dotnet workload install on CI to pin all agents to the
same workload set. This keeps developer machines unaffected (no global.json
workloadVersion) while ensuring CI builds are deterministic.

- Add -WorkloadSetVersion parameter to install-dotnet-workloads.ps1
- Add DOTNET_WORKLOAD_VERSION variable in azure-templates-variables.yml
- Pass the version through azure-templates-jobs-bootstrapper.yml

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

XHarness already disables the package verifier internally before
installing APKs. The 'android adb' subcommand doesn't exist in the
current dotnet-android tool, causing 'Unknown command' errors.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The test creates 4 native Skia objects per iteration (bitmap,
scaledBitmap, image, data) across 100 threads × 1000 iterations
(400K allocations) but never disposed them, relying solely on
GC finalization every 500ms. On CI agents with limited memory,
the GC couldn't keep up, causing 'Unable to allocate pixels'.

Add using declarations to all native objects so memory is released
deterministically. The test still validates threading correctness
(concurrent decode/scale/encode) while the GC background task
remains as additional stress.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

This reverts commit 4707163.

The --partition-size flag alone doesn't override the system image's
default userdata partition size. API 36 requires 7373 MB by default,
but CI agents only have ~6.5 GB free after build artifacts download.
The emulator starts in a degraded state (FATAL: not enough space) and
crashes during APK install with 'device offline'.

Restore the config.ini approach (disk.dataPartition.size=2048M) in
addition to the --partition-size flag, and log the full config.ini
contents for debugging.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The pinned build ID 155848 was used during development to speed up
CI iterations. Now that native builds are passing, revert to 'latest'
so the pipeline always uses the most recent native artifacts.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Local testing confirmed that:
- `--partition-size` acts as a floor: max(flag, system_image_default)
- API 36 system images already default to 6+ GB data partitions
- Setting config.ini disk.dataPartition.size is overwritten by the emulator
- Both the config.ini hack and --partition-size 2048 were no-ops

The INSTALL_FAILED_INSUFFICIENT_STORAGE issue was likely caused by the
emulator being offline, not by partition size.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Docker images for Linux/WASM builds have SDK 10.0.201 (feature band 2).
The previous pin to 10.0.100 with latestPatch only allowed 10.0.1xx,
causing all Linux and WASM native builds to fail with SDK not found.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Windows ANGLE agents have 10.0.102, Linux Docker images have 10.0.201.
Using 10.0.100 as the base version with latestFeature allows any 10.0.xxx
feature band to satisfy the requirement.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>